Q Project | Graded Directions: The format of the report will be as follows. Please include a demo video that shows the functionality and code. Submit it as a separate file. I. Title Page Include Title, Author, University, Course, Instructor, and Date For example: <Title of Project> By <Student Name> Florida Institute of Technology CIS 4498 for Dr. Bernard Parenteau Fall 2, 2022 II. Introduction In a nutshell, describe your project and how you did it. Provide justification as to why this is a worthy endeavor. Explain the practical applications of your project. This is an opportunity to sell your idea to the management of a company. This section should provide as many supporting materials for your project as is practical. If strong justification cannot be provided here, pursue another topic. III. Algorithms/Project Solution This section should describe your project design in detail. The information included in this section would be similar to what would be found in the Requirements Analysis and Design phases of the Systems Development Life Cycle (SDLC). You should detail all functions/pages/tabs/modules and the data in each. You should also describe your database design. IV. Implementation This section will describe all the technologies and resources that will be used to implement the projects. These will include programming languages, application frameworks (e.g., .NET, J2EE, etc.), database management systems, compilers, operating systems, and hardware platforms. You do not need to describe these (we all know what they are); just list them. If you are gathering data, describe the sources. If you are using existing packages or components, these should be noted here and briefly described if necessary. V. Results This section should describe your experience in implementing the solution. Describe any problems encountered, solutions implemented, and reasons for choosing that solution when multiple alternatives were available. Describe any deviations from your original plan. Also, describe any “lessons learned” that could be beneficial to future implementers. In addition, if the project involves analytics, a simulation, or comparative analysis, this section should describe the results. Use charts, graphs, and other means to summarize data if this would provide a clearer explanation of the results, and whether the results were as predicted ahead of time. Provide very detailed explanations of the results. VI. References This is required and especially important if you are using any existing code or other resources, in which case you should cite the source(s) here. VII. Appendices A. Status Reports This section will be a copy of the progress/status reports that have been submitted for the project during the semester. Progress/status reports should contain the following sections: • o ? Date: date of this report completed since the last status report ? Current activities: what is currently being worked on ? Challenges: what areas are time-consuming or causing problems ? Work to be completed: what needs to be completed for the next project milestone Rubric Final Report and Demo Video Rubric Final Report and Demo Video Rubric Criteria Ratings Pts This criterion is linked to a Learning OutcomeReport Content 10 to >5.0 pts Meets Expectations Thorough content 5 to >0 pts Needs Improvement Too brief or missing elements 10 pts This criterion is linked to a Learning OutcomeReport Format 5 to >3.0 pts Meets Expectations Correct format 3 to >0 pts Needs Improvement Incorrect format or missing sections 5 pts This criterion is linked to a Learning OutcomeDemo Video 5 to >3.0 pts Meets Expectations Clearly demonstrates all functions 3 to >0 pts Needs Improvement Missing features or not clear 5 pts Total Points: 20